Repository navigation
fix(android): discover SDK tools and explain device setup - #136
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Split from #132. Android discovery checks the SDK roots for each host and tells users whether they need Platform-Tools, the emulator, or a virtual device. A broken or missing emulator installation still permits discovery of authorized phones. The same setup hint reaches the panel and MCP clients.
The device guide, website, Claude requirements and bundled setup skill include the prerequisites, SDK Manager steps and host-specific paths. This change can ship to existing users independently of the Windows plugin launcher.
On Windows with Node 22.23.2, 65 SDK and panel tests plus targeted discovery and storage tests passed. An isolated MCP client with an empty PATH and no SDK received the installation instructions. Three existing Windows fixtures in the broader 80-test run require the host-specific test adaptations in #132. Existing telemetry is preserved.